Managing CDN registration by a storage provider

ABSTRACT

A system, method, and computer readable medium for managing registration, by a network storage provider, of one or more resources with a CDN service provider are provided. A network storage provider storing one or more resources on behalf of a content provider obtains registration information for registering the one or more resources with a CDN service provider. The registration information may include a request to publish one or more resources to a CDN service provider, an identification of the one or more resources, CDN selection criteria provided by the content provider or otherwise selected, and the like. The network storage provider transmits a CDN generation request corresponding to the registration information to the CDN service provider. Then, the network storage provider manages and processes data pursuant to registration of the one or more resources with the CDN service provider.

CROSS REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/272,666, entitled “MANAGING CDN REGISTRATION BY A STORAGE PROVIDER”and filed on Nov. 17, 2008, the disclosure of which is incorporatedherein by reference.

BACKGROUND

Generally described, computing devices and communication networks can beutilized to exchange information. In a common application, a computingdevice can request content from another computing device via thecommunication network. For example, a user at a personal computingdevice can utilize a software browser application to request a Web pagefrom a server computing device via the Internet. In such embodiments,the user computing device can be referred to as a client computingdevice and the server computing device can be referred to as a contentprovider.

Content providers are generally motivated to provide requested contentto client computing devices often with consideration of efficienttransmission of the requested content to the client computing deviceand/or consideration of a cost associated with the transmission of thecontent. For larger scale implementations, a content provider mayreceive content requests from a high volume of client computing deviceswhich can place a strain on the content provider's computing resources.Additionally, the content requested by the client computing devices mayhave a number of components, which can further place additional strainon the content provider's computing resources.

With reference to an illustrative example, a requested Web page, ororiginal content, may be associated with a number of additionalresources, such as images or videos, which are to be displayed with theWeb page. In one specific embodiment, the additional resources of theWeb page are identified by a number of embedded resource identifiers,such as uniform resource locators (“URLs”). In turn, software on theclient computing devices typically processes embedded resourceidentifiers to generate requests for the content. Often, the resourceidentifiers associated with the embedded resources reference a computingdevice associated with the content provider such that the clientcomputing device would transmit the request for the additional resourcesto the referenced content provider computing device. Accordingly, inorder to satisfy a content request, the content provider(s) (or anyservice provider on behalf of the content provider(s)) would provideclient computing devices data associated with the Web page and/or thedata associated with the embedded resources.

Some content providers attempt to facilitate the delivery of requestedcontent, such as Web pages and/or resources identified in Web pages,through the utilization of a network storage provider or a contentdelivery network (“CDN”) service provider. A network storage providerand a CDN server provider each typically maintains a number of computingdevices in a communication network that can maintain content fromvarious content providers. In turn, content providers can instruct, orotherwise suggest to, client computing devices to request some, or all,of the content provider's content from the network storage provider's orCDN service provider's computing devices.

As with content providers, network storage providers and CDN serviceproviders are also generally motivated to provide requested content toclient computing devices often with consideration of efficienttransmission of the requested content to the client computing deviceand/or consideration of a cost associated with the transmission of thecontent. Accordingly, CDN service providers often consider factors suchas latency of delivery of requested content in order to meet servicelevel agreements or to generally improve the quality of deliveryservice.

DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of thisinvention will become more readily appreciated as the same become betterunderstood by reference to the following detailed description, whentaken in conjunction with the accompanying drawings, wherein:

FIG. 1 is a block diagram illustrative of content delivery environmentincluding a number of client computing devices, a content provider, anetwork storage provider, and a content delivery network serviceprovider;

FIG. 2 is a block diagram of the content delivery environment of FIG. 1illustrating the registration of a content provider with a networkstorage provider;

FIG. 3A is a block diagram of the content delivery environment of FIG. 1illustrating the generation and processing of a CDN registration requestfrom a content provider to a network storage provider;

FIG. 3B is a block diagram of the content delivery environment of FIG. 1illustrating the registration, by a network storage provider, of one ormore resources with a content delivery network service provider;

FIG. 4A is a block diagram of the content delivery environment of FIG. 1illustrating one embodiment of the processing of resultant CDNregistration information;

FIG. 4B is a block diagram of the content delivery environment of FIG. 1illustrating another embodiment of the processing of resultant CDNregistration information;

FIG. 5 is a flow diagram illustrative of a CDN registration processingroutine implemented by a network storage provider; and

FIG. 6 is an illustrative user interface displaying information for usein registering with a content delivery network service provider.

DETAILED DESCRIPTION

Generally described, the present disclosure is directed to managingregistration of a content provider or one or more resources associatedwith a content provider with a content delivery network (“CDN”) serviceprovider. Specifically, aspects of the disclosure will be described withregard to the management and processing of CDN registration requestsmade to a network storage provider by a content provider. Althoughvarious aspects of the disclosure will be described with regard toillustrative examples and embodiments, one skilled in the art willappreciate that the disclosed embodiments and examples should not beconstrued as limiting.

FIG. 1 is a block diagram illustrative of content delivery environment100 for the managing registration of content with a CDN service providerand subsequent processing of content requests. As illustrated in FIG. 1,the content delivery environment 100 includes a number of clientcomputing devices 102 (generally referred to as clients) for requestingcontent from a content provider, a network storage provider 110, and/ora CDN service provider 106. In an illustrative embodiment, the clientcomputing devices 102 can correspond to a wide variety of computingdevices including personal computing devices, laptop computing devices,hand-held computing devices, terminal computing devices, mobile devices,wireless devices, various electronic devices and appliances and thelike. In an illustrative embodiment, the client computing devices 102include necessary hardware and software components for establishingcommunications over a communication network 108, such as a wide areanetwork or local area network. For example, the client computing devices102 may be equipped with networking equipment and browser softwareapplications that facilitate communications via the Internet or anintranet.

Although not illustrated in FIG. 1, each client computing device 102utilizes some type of local DNS resolver component, such as a DNS Nameserver, that generates the DNS queries attributed to the clientcomputing device. In one embodiment, the local DNS resolver componentmay be provide by an enterprise network to which the client computingdevice 102 belongs. In another embodiment, the local DNS resolvercomponent may be provided by an Internet Service Provider (ISP) thatprovides the communication network connection to the client computingdevice 102.

The content delivery environment 100 can also include a content provider104 in communication with the one or more client computing devices 102via the communication network 108. The content provider 104 illustratedin FIG. 1 corresponds to a logical association of one or more computingdevices associated with a content provider. Specifically, the contentprovider 104 can include a web server component 112 corresponding to oneor more server computing devices for obtaining and processing requestsfor content (such as Web pages) from the client computing devices 102.The content provider 104 can further include an origin server component114 and associated storage component 116 corresponding to one or morecomputing devices for obtaining and processing requests for networkresources. One skilled in the relevant art will appreciate that thecontent provider 104 can be associated with various additional computingresources, such additional computing devices for administration ofcontent and resources, DNS name servers, and the like. For example, asfurther illustrated in FIG. 1, the content provider 104 can beassociated with one or more DNS name server components 118 that areoperative to receive DNS queries related to registered domain namesassociated with the content provider. The one or more DNS name serverscan be authoritative to resolve client computing device DNS queriescorresponding to the registered domain names of the content provider104. A DNS name server component is considered to be authoritative to aDNS query if the DNS name server can resolve the query by providing aresponsive IP address.

With continued reference to FIG. 1, the content delivery environment 100can further include a CDN service provider 106 in communication with theone or more client computing devices 102, the content provider 104, andthe network storage provider 110 via the communication network 108. TheCDN service provider 106 illustrated in FIG. 1 corresponds to a logicalassociation of one or more computing devices associated with a CDNservice provider. Specifically, the CDN service provider 106 can includea number of Point of Presence (“POP”) locations 120, 126, 132 thatcorrespond to nodes on the communication network 108. Each POP 120, 126,132 includes a DNS component 122, 128, 134 made up of a number of DNSserver computing devices for resolving DNS queries from the clientcomputers 102. Each POP 120, 126, 132 also includes a resource cachecomponent 124, 130, 136 made up of a number of cache server computingdevices for storing resources from content providers or network storageproviders and transmitting various requested resources to various clientcomputers. The DNS components 122, 128, 134 and the resource cachecomponents 124, 130, 136 may further include additional software and/orhardware components that facilitate communications including, but notlimited, load balancing or load sharing software/hardware components.

In an illustrative embodiment, the DNS component 122, 128, 134 andresource cache component 124, 130, 136 are considered to be logicallygrouped, regardless of whether the components, or portions of thecomponents, are physically separate. Additionally, although the POPs120, 126, 132 are illustrated in FIG. 1 as logically associated with theCDN service provider 106, the POPs will be geographically distributedthroughout the communication network 108 in a manner to best servevarious demographics of client computing devices 102. Additionally, oneskilled in the relevant art will appreciate that the CDN serviceprovider 106 can be associated with various additional computingresources, such additional computing devices for administration ofcontent and resources, and the like.

With further continued reference to FIG. 1, the content deliveryenvironment 100 can also include a network storage provider 110 incommunication with the one or more client computing devices 102, the CDNservice provider 106, and the content provider 104 via the communicationnetwork 108. The network storage provider 110 illustrated in FIG. 1 alsocorresponds to a logical association of one or more computing devicesassociated with a network storage provider. Specifically, the networkstorage provider 110 can include a number of network storage providerPoint of Presence (“NSP POP”) locations 138, 142, 146 that correspond tonodes on the communication network 108. Each NSP POP 138, 142, 146includes a storage component 140, 144, 148 made up of a number ofstorage devices for storing resources from content providers which willbe processed by the network storage provider 110 and transmitted tovarious client computers. The storage components 140, 144, 148 mayfurther include additional software and/or hardware components thatfacilitate communications including, but not limited to, load balancingor load sharing software/hardware components.

In an illustrative embodiment, the storage components 140, 144, 148 areconsidered to be logically grouped, regardless of whether thecomponents, or portions of the components, are physically separate.Additionally, although the NSP POPs 138, 142, 146 are illustrated inFIG. 1 as logically associated with the network storage provider 110,the NSP POPs will be geographically distributed throughout thecommunication network 108 in a manner to best serve various demographicsof client computing devices 102. Additionally, one skilled in therelevant art will appreciate that the network storage provider 110 canbe associated with various additional computing resources, suchadditional computing devices for administration of content andresources, DNS name servers, and the like. For example, the networkstorage provider 110 can be associated with one or more DNS name servercomponents that are operative to receive DNS queries related toregistered domain names associated with the network storage provider110. The one or more DNS name servers can be authoritative to resolveclient computing device DNS queries corresponding to the registereddomain names of the network storage provider 110. As similarly set forthabove, a DNS name server component is considered to be authoritative toa DNS query if the DNS name server can resolve the query by providing aresponsive IP address.

Even further, one skilled in the relevant art will appreciate that thecomponents of the network storage provider 110 and components of the CDNservice provider 106 can be managed by the same or different entities.One skilled in the relevant art will also appreciate that the componentsand configurations provided in FIG. 1 are illustrative in nature.Accordingly, additional or alternative components and/or configurations,especially regarding the additional components, systems and subsystemsfor facilitating communications may be utilized.

With reference now to FIGS. 2-4B, the interaction between variouscomponents of the content delivery environment 100 of FIG. 1 will beillustrated. For purposes of the example, however, the illustration hasbeen simplified such that many of the components utilized to facilitatecommunications are not shown. One skilled in the relevant art willappreciate that such components can be utilized and that additionalinteractions would accordingly occur without departing from the spiritand scope of the present disclosure.

With reference to FIG. 2, an illustrative interaction for registrationof a content provider 104 with the network storage provider 110 will bedescribed. As illustrated in FIG. 2, the storage provider contentregistration process begins with registration of the content provider104 with the network storage provider 110. In an illustrativeembodiment, the content provider 104 utilizes a registration applicationprogram interface (“API”) to register with the network storage provider110 such that the network storage provider 110 can provide content onbehalf of the content provider 104. The registration API can include theidentification of the origin server 114 of the content provider 104 thatmay provide requested resources to the network storage provider 110. Inaddition or alternatively, the registration API can include the contentto be stored by the network storage provider 110 on behalf of thecontent provider 104. In one embodiment, the network storage provider110 may act as an origin server for the content provider 104.

One skilled in the relevant art will appreciate that upon storage of thecontent by the network storage provider 110, the content provider 104can begin to direct requests for content from client computing devices102 to the network storage provider 110. Specifically, in accordancewith DNS routing principles, a client computing device requestcorresponding to a resource identifier would eventually be directedtoward a storage component 140, 144, 148 of a NSP POP 138, 142, 146associated with the network storage provider 110.

With continued reference to FIG. 2, upon receiving the registration API,the network storage provider 110 obtains and processes the contentprovider registration information. In an illustrative embodiment, thenetwork storage provider 110 can then generate additional informationthat will be used by the client computing devices 102 as part of thecontent requests. The additional information can include, withoutlimitation, content provider identifiers, such as content provideridentification codes, storage provider identifiers, such as storageprovider identification codes, executable code for processing resourceidentifiers, such as script-based instructions, and the like. Oneskilled in the relevant art will appreciate that various types ofadditional information may be generated by the network storage provider110 and that the additional information may be embodied in any one of avariety of formats.

In one embodiment, the network storage provider 110 returns anidentification of applicable domains for the network storage provider(unless it has been previously provided) and any additional informationto the content provider 104. In turn, the content provider 104 can thenprocess the stored content with content provider specific information.In one example, as illustrated in FIG. 2, the content provider 104translates resource identifiers originally directed toward a domain ofthe origin server 114 to a domain corresponding to the network storageprovider 110. The translated URLs are embedded into requested content ina manner such that DNS queries for the translated URLs will resolve to aDNS server corresponding to the network storage provider 110 and not aDNS server corresponding to the content provider 104.

Generally, the identification of the resources originally directed tothe content provider 104 will be in the form of a resource identifierthat can be processed by the client computing device 102, such asthrough a browser software application. In an illustrative embodiment,the resource identifiers can be in the form of a uniform resourcelocator (“URL”). Because the resource identifiers are included in therequested content directed to the content provider, the resourceidentifiers can be referred to generally as the “content provider URL.”For purposes of an illustrative example, the content provider URL canidentify a domain of the content provider 104 (e.g.,contentprovider.com), a name of the resource to be requested (e.g.,“resource.xxx”) and a path where the resource will be found (e.g.,“path”). In this illustrative example, the content provider URL has theform of:

-   -   http://www.contentprovider.com/path/resource.xxx

During an illustrative translation process, the content provider URL ismodified such that requests for the resources associated with themodified URLs resolve to a POP associated with the network storageprovider 110. In one embodiment, the modified URL identifies the domainof the network storage provider 110 (e.g., “storageprovider.com”), thesame name of the resource to be requested (e.g., “resource.xxx”) and thesame path where the resource will be found (e.g., “path”). Additionally,the modified URL can include additional processing information (e.g.,“additional information”). The modified URL would have the form of:

-   -   http://additional        information.storageprovider.com/path/resource.xxx

In another embodiment, the information associated with the networkstorage provider 110 is included in the modified URL, such as throughprepending or other techniques, such that the translated URL canmaintain all of the information associated with the original URL. Inthis embodiment, the translated URL would have the form of:

-   -   http://additional        information.storageprovider.com/www.contentprovider.com/path/resource.xxx

With reference now to FIG. 3A, after completion of the network storageprovider registration and translation processes illustrated in FIG. 2,the network storage provider 110 subsequently causes the generation of auser interface or an API call to the content provider 104 for use indetermining whether the content provider 104 desires to register one ormore of the resources currently hosted by the network storage provider110 with a CDN service provider. The content provider 104 receives theCDN registration user interface, such as the user interface that will bedescribed in further detail below in reference to FIG. 6, or the APIcall from the network storage provider 110 via network 108. In anillustrative embodiment, the CDN registration user interface cancorrespond to a Web page that is displayed on a computing deviceassociated with the content provider 104, via the processing ofinformation, such as hypertext markup language (“HTML”), extensiblemarkup language (“XML”), and the like. As will be described furtherbelow in reference to FIGS. 5 and 6, the CDN registration user interfaceprovides the content provider 104 an option whether to have one or moreof the resources currently hosted by the network storage provider 110 onbehalf of the content provider 104 with a CDN service provider in thealternative. In the alternative, an API call would similarly provide thecontent provider 104 with an option to have one or more resources hostedby a CDN service provider.

In one embodiment, upon receipt of the CDN registration user interface,the content provider 104, such as through a browser softwareapplication, processes any of the markup code included in the CDNregistration user interface. The CDN registration user interfaceprovides a CDN selection component that the content provider 104 canselect to send a request to the network storage provider 110 via network108 to publish one or more resources to a CDN service provider. Uponselection of the CDN selection component, the content provider 104 sendsa corresponding CDN registration request to the network storage provider110 via network 108. As will also be further described below, other userinterface interaction information may also be provided to the networkstorage provider 110. For example, the content provider 104 may identifyvarious CDN selection criteria, such as a regional service plan or aservice level plan associated with a CDN service provider, via the CDNregistration user interface. The network storage service provider 110receives and processes the CDN registration request together with anyadditional information provided by the content provider 104.

With reference now to FIG. 3B, an illustrative interaction forregistration, by the network storage provider 110, of the one or moreresources associated with a content provider 104 with the CDN serviceprovider 106 will be described. As illustrated in FIG. 3B, the CDNcontent registration process begins with registration of the one or moreresources stored by the network storage provider 110 on behalf of thecontent provider 104 with the CDN service provider 106. In anillustrative embodiment, the network storage provider 110 utilizes aregistration application program interface (“API”) to register with theCDN service provider 106 such that the CDN service provider 106 canprovide the one or more resources on behalf of the network storageprovider 110 and further on behalf of the content provider 104. Theregistration API includes the identification of the storage component140, 144, 148 of the network storage provider 110 that will providerequested resources to the CDN service provider 106.

One skilled in the relevant art will appreciate that upon identificationof appropriate storage component 140, 144, 148 of the network storageprovider 110, the content provider 104 can, in one embodiment as will befurther described below in reference to FIG. 4A, begin to directrequests for content from client computing devices 102 to the CDNservice provider 106. Specifically, in accordance with DNS routingprinciples, a client computing device request corresponding to aresource identifier would eventually be directed toward a POP 120, 126,132 associated with the CDN service provider 106. In the event that theresource cache component 124, 130, 136 of a selected POP does not have acopy of a resource requested by a client computing device 102, theresource cache component will request the resource from the storagecomponent 140, 144, 148 of the network storage provider 110 previouslyregistered by the content provider 104.

With continued reference to FIG. 3B, upon receiving the registrationAPI, the CDN service provider 106 obtains and processes the registrationinformation. In an illustrative embodiment, the CDN service provider 106can then generate additional information that will be used by the clientcomputing devices 102 as part of the content requests. The additionalinformation can include, without limitation, content provideridentifiers, such as content provider identification codes, CDNidentifiers, such as CDN identification codes, executable code forprocessing resource identifiers, such as script-based instructions, andthe like. One skilled in the relevant art will appreciate that varioustypes of additional information may be generated by the CDN serviceprovider 106 and that the additional information may be embodied in anyone of a variety of formats. The CDN service provider 106 then returnsan identification of applicable domains for the CDN service provider(unless it has been previously provided) and any additional informationto the network storage provider 110.

In turn, with reference now to FIG. 4A, in one illustrative embodiment,the network storage provider 110 can then send a request to the contentprovider 104 to process the stored content with CDN provider specificinformation. In one example, as illustrated in FIG. 4A, the contentprovider 104 translates resource identifiers currently directed toward adomain of the network storage provider 110 to a domain corresponding tothe CDN service provider 106. The translated URLs are embedded intorequested content in a manner such that DNS queries for the translatedURLs will resolve to a DNS server corresponding to the CDN serviceprovider 106 and not a DNS server corresponding to the network storageprovider 110. Although the translation process is illustrated in FIG.4A, in some embodiments, the translation process may be omitted in amanner described in greater detail below.

Generally, the identification of embedded resources currently directedto the network storage provider 110 will be in the form of an embeddedresource identifier that can be processed by the client computing device102, such as through a browser software application. As similarly setforth above, in an illustrative embodiment, the embedded resourceidentifiers can be in the form of a uniform resource locator (“URL”).Because one or more resources are currently associated with the networkstorage provider 110, the corresponding embedded resource identifierscan be referred to generally as the “network storage provider URL.” Forpurposes of an illustrative example, the network storage provider URLcan identify a domain of the network storage provider 110 (e.g.,storageprovider.com), a name of the resource to be requested (e.g.,“resource.xxx”) and a path where the resource will be found (e.g.,“path”). In this illustrative example, the network storage provider URLhas the form of:

-   -   http://www.storageprovider.com/path/resource.xxx

During an illustrative translation process, the network storage providerURL is modified such that requests for the resources associated with thefurther translated URLs resolve to a POP associated with the CDN serviceprovider 106. In one embodiment, the translated URL identifies thedomain of the CDN service provider 106 (e.g., “cdnprovider.com”), thesame name of the resource to be requested (e.g., “resource.xxx”) and thesame path where the resource will be found (e.g., “path”). Additionally,the translated URL can include additional processing information (e.g.,“additional information”). The translated URL would have the form of:

-   -   http://additional_information.cdnprovider.com/path/resource.xxx

In another embodiment, the information associated with the CDN serviceprovider 106 is included the modified URL, such as through prepending orother techniques, such that the translated URL can maintain all of theinformation associated with the original URL. In this embodiment, thetranslated URL would have the form of:

-   -   http://additional_information.cdnprovider.com/www.storageprovider.com/path        /resource.xxx

With reference now to FIG. 4B, another embodiment of processinginformation as a result of registering one or more resources with theCDN provider 106 will be described. Instead of requesting the contentprovider 104 to translate one or more embedded resources to be providedby the CDN service provider 106 as described in reference to FIG. 4A,the network storage provider 110 may alternatively process CDNregistration information from the CDN service provider 106 itself suchthat the network storage provider 110 would provide an alternativeresource identifier responsive to a received client request for anembedded resource to the CDN service provider 106. Specifically, insteadof providing an embedded resource from a storage component 140, 144, 148of the network storage provider 110 upon receiving a request from aclient computing device 102 for the embedded resource, the networkstorage provider 110 can maintain sets of various alternative resourceidentifiers based on CDN registration information received from the CDNservice provider 106. The alternative resource identifiers can beprovided by the network storage provider 110 to the client computingdevice 102 such that a subsequent DNS query on the alternative resourceidentifier will resolve to a DNS server component within the CDN serviceprovider's network. In this embodiment, a DNS name server associatedwith the network storage provider 110 (directly or indirectly) is ableto receive the DNS query (corresponding to the domain in the embeddedresource). However, as discussed above, because the DNS name server doesnot provide a responsive IP address to the query, it is not consideredauthoritative to the DNS query. Instead, the network storage provider110 selects (or otherwise obtains) an alternative resource identifierthat is intended to resolve to an appropriate DNS server of the CDNservice provider 106 based on a variety of criteria. For example, thenetwork storage provider may select an alterative resource identifierbased on a regional service plan or service level information obtainedfrom the content provider. As will be described further below, thisadditional information may also be used for further request routing.

In an illustrative embodiment, the alternative resource identifiers arein the form of one or more canonical name (“CNAME”) records. In oneembodiment, each CNAME record identifies a domain of the CDN serviceprovider 106 (e.g., “cdnprovider.com” or “cdnprovider-1.com”). As willbe explained in greater detail below, the domain in the CNAME does notneed to be the same domain found in original URL. Additionally, eachCNAME record includes additional information, such as request routinginformation, (e.g., “request routing information”). An illustrativeCNAME record can have the form of:

-   -   request_routing_information.cdnprovider.com

In accordance with an illustrative embodiment, the network storageprovider 110 maintains a data store that defines CNAME records forvarious URLs corresponding to embedded resources stored by the networkstorage provider 110. If a DNS query corresponding to a particular URLmatches an entry in the data store, the network storage provider 110returns a CNAME record to the client computing device 102 as defined inthe data store and as illustrated in FIG. 4B.

The returned CNAME can also include request routing information that isdifferent from or in addition to the information provided in URL of thecurrent DNS query. For example, if the CNAME selection is based on aregional service plan or a service level plan selected by the contentprovider 104, a specific identifier can be included in the“request_routing_information” portion of the specific CNAME record. Inanother embodiment, request routing information can be found in theidentification of a CDN service provider 106 domain different from thedomain found in the original URL. For example, if the CNAME is based ona regional plan, a specific regional plan domain (e.g.,“cdnprovder-region1.com”) could be used in the domain name portion ofthe specific CNAME record. Any additional request routing informationcan be prepended to the existing request routing information in theoriginal URL such that the previous request routing information wouldnot be lost (e.g., http://serviceplan.regionalplan.cdnprovider.com). Oneskilled in the relevant art will appreciate that additional oralternative techniques and/or combination of techniques may be used toinclude the additional request routing information in the CNAME recordthat is identified by the network storage provider 110.

In another illustrative embodiment, prior to redirecting client DNSqueries for embedded resources to the CDN service provider 106, thenetwork storage provider 110 may also request that the content provider104 modify the original resource identifiers so that subsequent clientrequests for the embedded resources are directed to the network storageprovider 110 using a non-circular resource identifier.

With reference now to FIG. 5, one embodiment of a routine 500implemented by the network storage provider 110 for managingregistration of one or more resources stored on behalf of a contentprovider 104 with a CDN service provider 106 will be described. Oneskilled in the relevant art will appreciate that actions/steps outlinedfor routine 500 may be implemented by one or many computingdevices/components that are associated with the network storage provider110. Accordingly, routine 500 has been logically associated as beinggenerally performed by the network storage provider 110, and thus thefollowing illustrative embodiments should not be construed as limiting.

At block 502, the network storage provider 110 optionally obtains a CDNinquiry from a content provider 104 on behalf of which the networkstorage provider 110 hosts content. The CDN inquiry requests initialinformation regarding the potential use of a CDN service provider 106 toprovide one or more resources on behalf of the content provider 104. Inone embodiment, the content provider 104 may desire to registerindividual object files, such as those corresponding to embeddedresources. In addition or alternatively, the content provider 104 maydesire to register all objects associated with a resource, such as aparticular domain.

In response to the CDN inquiry or even without requiring an initial CDNinquiry, the network storage provider 110 causes a user interface forregistering one or more resources with a CDN service provider 106 to begenerated at block 504. The network storage provider 110 accordinglyobtains information to be provided as a part of the CDN registrationuser interface. For example, in one portion of the user interface, thenetwork storage provider 110 may provide, and hence obtain, anidentification of one or more resources currently hosted by the networkstorage provider 110 on behalf of the content provider 104, such as anembedded resource name, an embedded resource type, a current domainassociated with the embedded resource, a size of the embedded resource,and the like. The network storage provider 110 may also obtain andprovide additional information in the user interface, such as a numberof times each of the one or more resources has been requested by aclient computing device 102, a recommended CDN provider, an option toselect one or more available CDN service providers, one or more optionscorresponding to CDN selection criteria such as a regional service planor a service level plan, and the like. Even further, the CDNregistration user interface includes a CDN selection component thatprovides a content provider an option to initiate publication of the oneor more resources to a CDN service provider.

In one illustrative embodiment, rather than obtaining an initial CDNinquiry from a content provider 104, the network storage provider 110may determine that a recommendation to use a CDN to provide a particularresource should be provided. Based on this determination, the networkstorage provider 110 would cause the CDN registration user interface tobe generated. For example, the network storage provider 110 may monitorthe volume of requests for each resource. If an embedded resource, suchas one with a relatively large file size, has been requested a highnumber of times, the network storage provider 110 may determine thatthis embedded resource is a candidate for being provided by a CDNservice provider and accordingly generate a correspondingrecommendation.

In another illustrative embodiment, the network storage provider 110 candetermine whether to make a CDN recommendation based on a variety ofcriteria, such as cost to the content provider, quality of service,throughput, content provider contractual obligations, latency, internetweather, and the like. Even further, the network storage provider 110can utilize a web service to determine whether to make a particular CDNrecommendation. For example, the network storage provider 110 canutilize the testing system disclosed in U.S. patent application Ser. No.12/240,740, titled “Service Provider Optimization of Content Management”and hereby incorporated by reference, to make CDN recommendations. Yetfurther, in other embodiments, the network storage provider 110 canrecommend registration with one or more CDN service providers.

Continuing with FIG. 5, at block 506, the network storage provider 110obtains CDN provider registration information from the content provider104. The CDN provider registration information includes a request fromthe content provider 104 to publish one or more resources to a CDNservice so that the CDN service provider 106 provides the one or moreresources on behalf of the content provider 104. The CDN providerregistration information can also include other information obtainedfrom the content provider 104 such as an identification of a particularCDN service provider, a select regional plan, a select service levelplan, and the like. The network storage provider 110 also obtains anyadditional CDN provider registration information, whether from thecontent provider or otherwise, which may be needed to register the oneor more resources with the CDN service provider. The additional CDNprovider registration information may include an identification of theone or more resources requested to be published to a CDN service,content provider billing information, network storage provider billinginformation, and the like. As similarly set forth above, theidentification information associated with the one or more resources mayinclude any one or more of the embedded resource name, the embeddedresource type, the current domain, the size of the embedded resource,and the like. In one illustrative embodiment, the network storageprovider 110 obtains all CDN provider registration information necessaryto register the one or more resources with the CDN service provider 106on behalf of the content provider 104 in a single request.

Next, at block 508, the network storage provider 110 transmits a CDNgeneration request associated with the obtained CDN registrationinformation to the CDN service provider 106. At block 510, the networkstorage provider 110 then processes data corresponding to the resultantregistration of the one or more resources with the CDN service provider.In one illustrative embodiment, the network storage provider 110requests or otherwise causes the content provider 104 to modify one ormore resource identifiers corresponding to the one or more resources sothat subsequent requests for the one or more resources are directed tothe CDN service provider 106. In an alternative embodiment, the networkstorage provider 110 obtains an alternative resource identifiercorresponding to each of the one or more resources so that the networkstorage provider 110 can redirect client requests for the one or moreresources to the CDN service provider 106. In either of the foregoingembodiments, the network storage provider 110 may also notify thecontent provider 104 that the one or more resources have been registeredwith the CDN service provider 106. The routine 500 ends at block 512.

Although many of the above described embodiments disclose use a userinterface and receive input responsive to human interaction, the contentprovider 104 and the network storage provider 110 may interact via aseries of API calls. In such embodiments, the content provider 104 orthe network storage provider 110 may programmatically process the APIs,e.g., in accordance with defined business rules or other logic such thatadditional human interaction is not necessary. Accordingly, the presentapplication should not be limited to use of a user interface. Forexample, rather than generating a user interface at block 504, thenetwork storage provider 110 may generate an API call to the contentprovider 104 similarly requesting a determination be made regardingwhether a CDN service provider should be used to host content on behalfof the content provider 104. Likewise, the content provider 104 canautomatically process the API and return information to the networkstorage provider 110.

With reference now to FIG. 6, one illustrative embodiment of a userinterface or screen display 600 in which information for registering oneor more resources with a CDN service provider 106 will now be described.In this illustrative embodiment, the screen display 600 is a Web pageillustrating a presentation of content regarding the potentialregistration of a particular resource with a CDN service provider 106.The screen display 600 includes a CDN selection component 618 which whenselected causes a request to register the identified resource with a CDNservice provider 106 to be sent to the network storage provider 110. Inone embodiment, with respect to a particular embedded resource, thescreen display 600 also includes information identifying the embeddedresource, such as an embedded resource name 602, an embedded resourcetype 604, a current domain associated with the embedded resource 606,and a size of the embedded resource 608. The screen display 600 furtherincludes information identifying a number of times the embedded resourcehas been requested from the network storage provider 110, as well as alink 610 corresponding to an identifier that when selected provides moredetailed information regarding client requests for the embeddedresource. In another embodiment, where the resource corresponds to adomain of the content provider, the screen display 600 could alsosimilarly include information associated with the domain, such as adomain identification, a number of requests associated with the domain,a number of embedded resources associated with the domain, and the like.

In another portion of the screen display 600, CDN selection criteria areprovided. For example, a regional plan selection component 612 and aservice level selection component 614 are provided to allow the contentprovider 104 to select desired parameters associated with a CDN serviceprovider 106. Finally, the display screen 600 includes a specific CDNservice provider recommendation 616 generated by the network storageprovider 110. As similarly set forth above, the recommendation mayidentify one or more CDN service providers for hosting content on behalfof the content provider.

It will be appreciated by those skilled in the art and others that allof the functions described in this disclosure may be embodied insoftware executed by one or more processors of the disclosed componentsand mobile communication devices. The software may be persistentlystored in any type of non-volatile storage.

Conditional language, such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, or otherwise understoodwithin the context as used, is generally intended to convey that certainembodiments include, while other embodiments do not include, certainfeatures, elements and/or steps. Thus, such conditional language is notgenerally intended to imply that features, elements and/or steps are inany way required for one or more embodiments or that one or moreembodiments necessarily include logic for deciding, with or without userinput or prompting, whether these features, elements and/or steps areincluded or are to be performed in any particular embodiment.

Any process descriptions, elements, or blocks in the flow diagramsdescribed herein and/or depicted in the attached Figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or steps in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved, as would be understood by those skilled in the art. It willfurther be appreciated that the data and/or components described abovemay be stored on a computer-readable medium and loaded into memory ofthe computing device using a drive mechanism associated with a computerreadable storing the computer executable components such as a CD-ROM,DVD-ROM, or network interface further, the component and/or data can beincluded in a single device or distributed in any manner. Accordingly,general purpose computing devices may be configured to implement theprocesses, algorithms and methodology of the present disclosure with theprocessing and/or execution of the various data and/or componentsdescribed above.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure and protected by the following claims.

1. A computer implemented method comprising: determining that use of acontent delivery network (CDN) service provider should be recommended bya network storage provider to a content provider based on an evaluationof past requests made to the network storage provider for one or moreresources, wherein the one or more resources are stored and provided bythe network storage provider on behalf of the content provider;obtaining registration information at the network storage provider forregistering one or more resources associated with the content providerwith a CDN service provider; and transmitting a CDN generation requestfrom the network storage provider to a CDN service provider, the CDNgeneration request corresponding to the registration information.
 2. Thecomputer implemented method as recited in claim 1, wherein the one ormore resources correspond to one or more embedded resources.
 3. Thecomputer implemented method as recited in claim 1, wherein theregistration information includes identification of the one or moreresources to be provided by a CDN service provider and CDN selectioncriteria provided by the content provider.
 4. The computer implementedmethod as recited in claim 1 further comprising: causing generation, bythe network storage provider, of a user interface for registering theone or more resources with a CDN service provider.
 5. The computerimplemented method as recited in claim 4, wherein the user interfaceprovides an option for a content provider to select to register with aCDN service provider by selection of a single control.
 6. The computerimplemented method as recited in claim 4, wherein the user interfaceprovides identification of one or more recommended CDN serviceproviders.
 7. The computer implemented method as recited in claim 4further comprising: obtaining a CDN inquiry from a content provider atthe network storage provider, wherein the CDN inquiry corresponds to aninitial request to register one or more resources with a CDN serviceprovider.
 8. The computer implemented method as recited in claim 1further comprising: causing generation, by the network storage provider,of an API call for registering the one or more resources with a CDNservice provider.
 9. The computer implemented method as recited in claim1 further comprising: notifying the content provider of the registrationof the one or more resources with the CDN service provider withoutreceiving a request from the content provider for the notification. 10.The computer implemented method as recited in claim 1 furthercomprising: sending a request from the network storage provider for thecontent provider to modify one or more resource identifierscorresponding to the one or more resources so that subsequent requestsfor the one or more resources are directed to a CDN service provider.11. The computer implemented method as recited in claim 1 furthercomprising: obtaining, at the network storage provider, an alternativeresource identifier corresponding to each of the one or more resources,wherein the alternative resource identifier corresponds to anidentification of a CDN service provider for providing the associatedresource.
 12. A non-transitory computer readable medium for storingcomputer executable components for managing registration of content witha CDN service provider, the computer readable medium comprising: a firstcomponent for identifying one or more resources associated with acontent provider and determining that use of a content delivery network(CDN) service provider should be recommended by a network storageprovider to the content provider based on an evaluation of past requestsmade to the network storage provider for the one or more resources,wherein the one or more resources are stored by the network storageprovider on behalf of the content provider; and a second component thatwhen selected causes the network storage provider to register the one ormore resources with a CDN service provider.
 13. The non-transitorycomputer readable medium as recited in claim 12, wherein the firstcomponent further comprises identifying a current storage location ofeach of the one or more resources.
 14. The non-transitory computerreadable medium as recited in claim 12, wherein the first componentfurther comprises identifying a number of prior requests made to thenetwork storage component for each of the one or more resources.
 15. Thenon-transitory computer readable medium as recited in claim 12 furthercomprising: a third component for identifying one or more recommendedCDN service providers based on information associated with the one ormore resources.